OpenSim versions are inconsistant about how they report OS threat level failures. 🔼
Threat level errors look like this (at least in OpenSim 0.8.2) -
OSSL Runtime Error: osSetStateEvents permission denied. Script creator is not in the list of users allowed to execute this function and prim owner also has no permission.
There is also (OpenSim 0.9.1) -
Max Zephyr script
OSSL Runtime Error: permission denied. All OS functions are disabled.(script: oc_settings event: changed primID:487baa88-d6e5-420c-b18c-f47f5bbd7de4 at <127.9408, 128.0009, 25.75689>)
My script
OSSL Runtime Error: osSetSpeed permission denied. All OS functions are disabled.(script: 1AOor2 event: changed primID:c7db8d3c-ae33-44ce-a685-cf63a37f0cf5 at <123.933, 203.0375, 24.29473>)
From the source (NOTE: first version has no function name) -
("{0} permission denied. All OS functions are disabled.")
("{0} permission denied. All OS functions are disabled.", function)
("{0} permission denied. Allowed threat level is {1} but function threat level is {2}.", function,
("{0} permission denied. Script creator is not in the list of users allowed to execute this function and prim owner also has no permission.", function
("{0} permission denied. Script permissions error.", function
OpenSim 0.9.0.1 doesn't include the "OSSL Runtime Error: " bit at the beginning anymore.
OpenSim 0.9.1 seems to not even send it to the DEBUG_CHANNEL for scripts anymore.
The various versions may or may not include a stack trace, which in some versions you can disable.
Even OpenSims own script for detecting threat level failures doesn't work.
reported=2019-06-20 18:37:12
reporter=onefang
priority=low
category=Bug
severity=minor
resolution=fixed
2019-07-24 15:07:20 onefang: Currently it all works as expected. Let's keep it that way.